This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
Status 2 #668
Merged
Status 2 #668
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
August 23, 2023 10:48
decentralgabe
requested review from
nitro-neal and
andresuribe87
as code owners
decentralgabe
added a commit
that referenced
this pull request
Aug 23, 2023
* adding in seperate status base URI * Update config/info.go Co-authored-by: Gabe <[email protected]> * Update config/info.go Co-authored-by: Gabe <[email protected]> * Update config/info.go Co-authored-by: Gabe <[email protected]> * fixing for default and gabes feedback * Status (#666) * tmp * fix tests * Update integration/common.go * Status 2 (#668) * tmp * fix tests * fix int test * fix config * Update integration/common.go --------- Co-authored-by: Gabe <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Include a summary of the change and link to the issue it addresses.
Description
Include context, motivation, brief description, and an impact of the change(s). List follow-up tasks here.
How Has This Been Tested?
Describe the tests that you ran to verify your changes. Provide instructions for verification.
Checklist
Before submitting this PR, please make sure:
References
Please list relevant documentation (e.g. tech specs, articles, follow up or related work) relevant to this change, and note if the documentation has been updated.